Hi Tom,

Testing with 433L is going well, no problems so far. I have a few comments and questions about packaging up our custom CNC app (based on KMotionCNC):

There is an incompatibility with our app and KMotion.exe. The latter is currently compiled for older versions of the MFC DLLs (v. 9), and thus if we try to mix it with our stuff compiled to use the version 12 we get crashes when trying to use KMotion.exe to do basic set-up and tuning. My guess is that it is trying to use KMotionDLL.dll, but since that is compiled with VS2013 there's a fundamental incompatibility.

So there's a couple of things we can do to get around that:

(a) Have a separate install step for KMotion and our software. Our software would be pared down to the minimum required for the custom CNC app, be in a separate folder etc. (We already have this working).

(b)You could provide a release of KMotion433L compiled with VS2013. - at least KMotion.exe.

(d) We could repackage KMotion433L and live with having multiple versions of the DLLs around.

(e) We could eliminate the requirement for KMotion.exe, by adding the functionality we need into the custom app.

We would rather avoid (a) because of the additional complexity for our end users, and because a lot of extra stuff would be installed which most users would not want, and may be a potential source of tech support questions to us. (Ooooh - what's this dot net stuff? - double click - argh!)

(b) or (c) would be good from our point of view. Any possibility of that?

(d) we could probably work out now if it was the only option.

Regarding (e), the main use we have for KMotion.exe is to download and flash a couple of threads which we need to compile with cl6x. And obviously we use it "back in the factory" for tuning and debugging, but that's no concern for our customers.

So if there was a way of emulating the flash commands (updates to Kflop firmware and our user programs) from our custom app then that would mostly obviate the need for customers to have KMotion.exe.

Is that possible? Any sample code to do this?

Finally, our installer can look for existing installations. I noticed you set a registry key HKLM/software/.../dynomotion/kmotion/2.2. Is that a reasonable key to search for if our installer is checking that KMotion is installed?

Regards,

SJH

Group: DynoMotion	Message: 11727	From: Hardy Family	Date: 6/19/2015
Subject: Packaging custom KMotionCNC, VS2013

Group: DynoMotion	Message: 11737	From: Tom Kerekes	Date: 6/21/2015
Subject: Re: Packaging custom KMotionCNC, VS2013